|
|
|
|||
|
|
|
|
|
FEEDBACK
EarthWeb sites
|
|
The RegistryThe Registry acts as a configuration database and contains virtually all of the Windows NT user and system configuration data. The data contained in the Registry is organized in a tree format, similar to how folders and files are stored on a disk. The Registry is split into five subtrees, which contain keys and subkeys. These keys can contain data items known as value entries. The value entries are constructed in three parts: the value name, the data type of the value, and the actual value data. For example, you can see these parts in the Registry entry ServiceName:REG_SZ:Browser. Table 1.2 lists the data types used by the Registry.
In addition, the Registry has collections of keys, subkeys, and value entries called hives that start at the root of the Registry. The HKEY_LOCAL_MACHINE\System hive is shown in Figure 1.1. A hive is contained in a single file contained in the %SYSTEMROOT%\SYSTEM32\CONFIG folder. Table 1.3 provides an overview of each Registry subtree.
The administrator usually manages the Registry indirectly by using the system administration tools that automatically perform the necessary configuration changes to the Registry. If the change you require can’t be achieved with the administration tools, you can use the Registry Editor REGEDT32 to make manual changes. Great care should be taken when using the Registry Editor; Windows NT can be rendered inoperative by incorrect changes to the Registry. Because of the importance of the Registry to Windows NT, all changes to the Registry are either completed or not made. In other words, should the system fail for any reason while several Registry entries are being changed (often an administration tool must change several Registry entries for a new configuration to be implemented), the Registry would ensure that all the required entries are changed or that no changes are made, thus leaving the Registry in a known state. Workgroups And DomainsWindows NT can be used in either a workgroup or domain configuration. The main points of both configurations are pointed out in the following sections. WorkgroupEach computer participating in a workgroup is considered to be equal. A Security Account Manager (SAM) database is held on each computer in the workgroup. The workgroup is defined as functioning on a peer-to-peer basis. Because each computer holds its own SAM, the administration of the workgroup must be performed locally on each computer in the workgroup. The security policies are set on a system-wide basis. A workgroup configuration is usually only suitable for small numbers of users and computers. DomainAll computers participating in a domain use a central domain SAM. The domain database is managed by Windows NT servers. (Details of the roles played by Windows NT servers in a domain can be found in Chapter 7.) Because a central domain database is used, the administration of the domain is also centralized, making the domain model suitable for larger numbers of computers and users. The security policies are set on a domain-wide basis. Projects:
|
||||||||||||||||||||||||||||||||||||||||||||
| Previous | Table of Contents | Next |
|
|
|
)
){kind=link}